docs/content/1.guides/6.notifications.md (1)

6-8: ⚠️ Potential issue | 🟡 Minor

Rename provider section to “Setup.”

Line 6 should use “Setup” for provider registration sections to match documentation standards.
As per coding guidelines: Use 'Setup' for provider registration sections in documentation.

docs/content/1.guides/4.authentication.md (2)

6-8: ⚠️ Potential issue | 🟡 Minor

Rename provider section to “Setup.”

Line 6 should use “Setup” for provider registration sections.
As per coding guidelines: Use 'Setup' for provider registration sections in documentation.

---

150-191: ⚠️ Potential issue | 🟡 Minor

Add a Success Flow for useAuthenticated and useGetIdentity.

Both Composition sections list Data Composables and Actions but omit Success Flow; the controller doc standard requires all three elements.
Based on learnings: When documenting high-level Controllers, always explain their Composition including Data Composables, Actions, and Success Flow.

docs/content/1.guides/8.resources.md (1)

6-8: ⚠️ Potential issue | 🟡 Minor

Rename provider section to “Setup.”

Line 6 should use “Setup” for provider registration sections.
As per coding guidelines: Use 'Setup' for provider registration sections in documentation.

docs/content/1.guides/7.realtime.md (1)

6-8: ⚠️ Potential issue | 🟡 Minor

Rename provider section to “Setup.”

Line 6 should use “Setup” for provider registration sections.
As per coding guidelines: Use 'Setup' for provider registration sections in documentation.

README.md (2)

35-35: ⚠️ Potential issue | 🟡 Minor

Remove numbered prefix from headers.

The header uses a numbered prefix "1. Installation" which violates the coding guideline. As per coding guidelines, do not use numbered headers or redundant suffixes in documentation headers.

📝 Proposed fix

-**1. Installation**
+**Installation**

---

41-41: ⚠️ Potential issue | 🟡 Minor

Remove numbered prefix from headers.

The header uses a numbered prefix "2. Usage" which violates the coding guideline. As per coding guidelines, do not use numbered headers or redundant suffixes in documentation headers.

📝 Proposed fix

-**2. Usage**
+**Usage**

docs/content/3.backend/supabase.md (1)

39-73: ⚠️ Potential issue | 🟡 Minor

Backend Setup section should demonstrate integration with Nuxt.

The Setup section currently shows Vue and Svelte examples, but according to the coding guidelines, backend documentation should include a Setup section demonstrating integration with all supported frontend frameworks (Vue and Nuxt). The Svelte example can be optional, but Nuxt integration should be included.

Based on learnings: Backend documentation should include a Setup section demonstrating integration with all supported frontend frameworks (Vue and Nuxt).

📝 Suggested addition for Nuxt example

Add a Nuxt tab to the code-group:

<script setup lang="ts">
import { defineAuthContext, defineFetchersContext } from '@ginjou/vue'
import { createAuth, createFetcher } from '@ginjou/with-supabase'
import { createClient } from '@supabase/supabase-js'

const supabaseUrl = 'https://your-project.supabase.co'
const supabaseKey = 'your-anon-key'
const client = createClient(supabaseUrl, supabaseKey)

defineFetchersContext({
	default: createFetcher({ client })
})

defineAuthContext(createAuth({ client }))
</script>

<template>
	<NuxtLayout>
		<NuxtPage />
	</NuxtLayout>
</template>

docs/content/3.backend/rest-api.md (1)

39-68: ⚠️ Potential issue | 🟡 Minor

Backend Setup section should demonstrate integration with Nuxt.

The Setup section currently shows Vue and Svelte examples, but according to the coding guidelines, backend documentation should include a Setup section demonstrating integration with all supported frontend frameworks (Vue and Nuxt). While Svelte can be optional, Nuxt integration should be included.

Based on learnings: Backend documentation should include a Setup section demonstrating integration with all supported frontend frameworks (Vue and Nuxt).

📝 Suggested addition for Nuxt example

Add a Nuxt tab to the code-group:

<script setup lang="ts">
import { defineFetchersContext } from '@ginjou/vue'
import { createFetcher } from '@ginjou/with-rest-api'

defineFetchersContext({
	default: createFetcher({
		url: 'https://api.example.com'
	})
})
</script>

<template>
	<NuxtLayout>
		<NuxtPage />
	</NuxtLayout>
</template>

docs/content/3.backend/directus.md (1)

39-73: ⚠️ Potential issue | 🟡 Minor

Missing Nuxt setup example; replace Svelte WIP placeholder.

The Setup section currently shows Vue and a Svelte WIP placeholder, but is missing a Nuxt example. As per coding guidelines, backend documentation should include a Setup section demonstrating integration with all supported frontend frameworks (Vue and Nuxt). The Svelte block provides no implementation and should either be completed or removed.

📋 Recommended structure

Replace the Svelte WIP block with a Nuxt example:

 ```vue [Vue]
 <script setup lang="ts">
 import { authentication, createDirectus, rest } from '@directus/sdk'
 import { defineAuthContext, defineFetchersContext } from '@ginjou/vue'
 import { createAuth, createFetcher } from '@ginjou/with-directus'
 
 const client = createDirectus('https://your-directus-url.com')
 	.with(rest())
 	.with(authentication())
 
 defineFetchersContext({
 	default: createFetcher({ client })
 })
 
 defineAuthContext(createAuth({ client }))
 </script>
 
 <template>
 	<RouterView />
 </template>

-```svelte [Svelte]
-
-<script>

• // ...
  -</script>
  +```vue [Nuxt]
  +<script setup lang="ts">
  +import { authentication, createDirectus, rest } from '@directus/sdk'
  +import { defineAuthContext, defineFetchersContext } from '@ginjou/nuxt'
  +import { createAuth, createFetcher } from '@ginjou/with-directus'

+const client = createDirectus('https://your-directus-url.com')

• .with(rest())
• .with(authentication())

+defineFetchersContext({

• default: createFetcher({ client })
  +})

+defineAuthContext(createAuth({ client }))
+</script>
+
+

+

Based on learnings: Backend documentation should include a Setup section demonstrating integration with all supported frontend frameworks (Vue and Nuxt).

docs/content/1.guides/0.introduction.md (1)

106-134: ⚠️ Potential issue | 🟠 Major

Mermaid diagram should show data flow, not just call hierarchy.

The current graph is primarily a dependency/call hierarchy. Please switch to a flow/sequence diagram that shows how data moves between layers (e.g., UI → controller → composables → fetcher → backend → cache → UI).
As per coding guidelines: "Use Mermaid diagrams in documentation to show logic flow and how data moves, not just call hierarchies".

docs/content/1.guides/8.resources.md (1)

6-26: 🛠️ Refactor suggestion | 🟠 Major

Add a dedicated "Setup" section for provider registration.

The document introduces resource concepts but doesn't provide a clear "Setup" section showing how to register the resource provider. The actual registration code (defineResourceContext) appears later in the "Multiple Fetchers" section (line 257), making it difficult for developers to understand basic setup.

As per coding guidelines, use 'Setup' for provider registration sections in documentation. Add a Setup section after line 26 demonstrating basic resource provider registration for both Vue and Nuxt before diving into specific patterns.

📝 Suggested Setup section

Add after line 26:

## Setup

Register your resources using the resource provider context:

::code-group
---
sync: guide-example
---

```vue [Vue]
<script setup lang="ts">
import { defineResourceContext } from '@ginjou/vue'

const resources = [
	{
		name: 'posts',
		list: '/posts',
		create: '/posts/new',
		edit: '/posts/:id/edit',
		show: '/posts/:id',
	},
]

defineResourceContext({ resources })
</script>

<script setup lang="ts">
// In app.vue or app/app.vue
import { defineResourceContext } from '@ginjou/nuxt'

const resources = [
	{
		name: 'posts',
		list: '/posts',
		create: '/posts/new',
		edit: '/posts/:id/edit',
		show: '/posts/:id',
	},
]

defineResourceContext({ resources })
</script>

::

</details>

</blockquote></details>

</blockquote></details>

🤖 Fix all issues with AI agents

In `@docs/content/1.guides/0.introduction.md`:
- Around line 142-151: Update the useList example to explicitly describe its
Controller composition: list the Data Composables (e.g., useGetList for
fetching, any query/state hooks), the Actions provided by useList (e.g.,
refresh, applyFilters, paginate — reference useGo/useLocation where URL-sync
actions occur), and the Success Flow (how useNotify and useTranslate are invoked
on successful operations and how success handlers propagate results). Mention
the lower-level composables that can be combined (useGetList, useGo,
useLocation) and state that useList wires those data composables, exposes action
methods, and triggers notify/translate on success so readers see Data
Composables, Actions, and Success Flow explicitly.

In `@docs/package.json`:
- Line 13: The dependency "docus": "^5.5.0" in package.json is invalid (no such
version on npm); update the version spec for the "docus" dependency to a
published release such as "^4.1.3" or confirm and replace it with the correct
pre-release/private-registry spec, then run npm install to verify; locate the
"docus" entry in package.json to make this change.

🧹 Nitpick comments (2)

docs/content/1.guides/8.resources.md (2)

184-189: Complete Svelte examples for framework parity.

Multiple Svelte examples are marked as "WIP" throughout the document (also at lines 278-283). While Vue examples are comprehensive, the incomplete Svelte code reduces documentation utility for Svelte users.

---

252-276: Consider showing usage of destructured variables.

Lines 268-274 destructure records and data from useList but don't demonstrate their usage in the template or elsewhere. For documentation clarity, either show how these variables are used or simplify the example to focus on the fetcher configuration aspect.

docs/content/3.backend/supabase.md (1)

35-73: ⚠️ Potential issue | 🟠 Major

Missing Nuxt integration example in Setup section.

The Setup section currently only demonstrates Vue integration. As per coding guidelines, backend documentation should include Setup examples for all supported frontend frameworks (Vue and Nuxt). The Nuxt example should show the proper root component setup with <NuxtPage /> instead of <RouterView />.

As per coding guidelines: "Backend documentation should include a Setup section demonstrating integration with all supported frontend frameworks (Vue and Nuxt)"

📝 Suggested Nuxt example to add

Add a Nuxt tab to the code-group:

<script setup lang="ts">
import { defineAuthContext, defineFetchersContext } from '@ginjou/nuxt'
import { createAuth, createFetcher } from '@ginjou/with-supabase'
import { createClient } from '@supabase/supabase-js'

const supabaseUrl = 'https://your-project.supabase.co'
const supabaseKey = 'your-anon-key'
const client = createClient(supabaseUrl, supabaseKey)

defineFetchersContext({
	default: createFetcher({ client })
})

defineAuthContext(createAuth({ client }))
</script>

<template>
	<NuxtPage />
</template>

docs/content/3.backend/directus.md (1)

35-73: ⚠️ Potential issue | 🟠 Major

Missing Nuxt integration example in Setup section.

The Setup section currently only demonstrates Vue integration. As per coding guidelines, backend documentation should include Setup examples for all supported frontend frameworks (Vue and Nuxt). The Nuxt example should show the proper root component setup with <NuxtPage /> instead of <RouterView />.

As per coding guidelines: "Backend documentation should include a Setup section demonstrating integration with all supported frontend frameworks (Vue and Nuxt)"

📝 Suggested Nuxt example to add

Add a Nuxt tab to the code-group:

<script setup lang="ts">
import { authentication, createDirectus, rest } from '@directus/sdk'
import { defineAuthContext, defineFetchersContext } from '@ginjou/nuxt'
import { createAuth, createFetcher } from '@ginjou/with-directus'

const client = createDirectus('https://your-directus-url.com')
	.with(rest())
	.with(authentication())

defineFetchersContext({
	default: createFetcher({ client })
})

defineAuthContext(createAuth({ client }))
</script>

<template>
	<NuxtPage />
</template>